DM-4340: Don't render RECAPTCHA if key isn't available #748
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Closing this PR since we'll be removing the relevant form. |
PhilipDeFraties
approved these changes
Dec 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA issue link
DM-4340
Description - what does this code do?
Testing done - how did you test it/steps on how can another person can test it
RECAPTCHA_SITE_KEY_V3is not present in your local.envfile.master, start local dev and navigate toAbout.Recaptcha::RecaptchaError in About#index No site key specified.Aboutpage. The form should still render. Check the inspector and confirm that no recaptcha snippet is loaded.